✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	3f6928e
🔍 Latest deploy log	https://app.netlify.com/sites/biomejs/deploys/661e283d928b78000868bef6
😎 Deploy Preview	https://deploy-preview-2480--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (🔴 down 5 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 93 (no change from production) PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Parser conformance results on

js/262

jsx/babel

symbols/microsoft

ts/babel

ts/microsoft

CodSpeed Performance Report

Merging #2480 will improve performances by 6.67%

_{Comparing chore/tidy-up-crates (3f6928e) with main (d4b2d3e)}

Summary

⚡ 1 improvements
✅ 92 untouched benchmarks

Benchmarks breakdown

I'm having some weird issues when running cargo build --lib --target wasm32-unknown-unknown in crates/biome_wasm.

At first it emits:

...
error: could not compile `hashbrown` (lib) due to 807 previous errors

And now it emits sth like:

...
error[E0599]: no function or associated item named `new` found for struct `IndexMap` in the current scope
...
error: could not compile `biome_js_parser` (lib) due to 4 previous errors

And sometimes it can be built successfully.

Is this related to this PR? This issue now breaks the website pnpm build:wasm or pnpm build:wasm-dev. But strange enough the build script on netlify seems working well.

Edit:

Ah, nevermind. I think this is caused by the cached target dir. It works when I delete it and rebuild everything.